Никто из сотрудников финансового офиса не может издавать приказы, финансовые директивы или рекомендации, которые каким либо образом уста навливают оргполитику, изменяют оргполитику или отменяют оргполитику, поскольку это может быть сделано только в инструктивных письмах по орг политике, должным образом утверждённых и опубликованных на тех линиях, которые имеют на это право.

An Esto, as well as being mobile, must not get “stuck in” on one point of a division or org.

Все такого рода приказы и все финансовые директивы настоящим отменя1 ются.

Spending days hatting only one staff member and letting whole departments go is an example of what is meant by “getting stuck in.”

В решении финансовых вопросов нужно следовать только соответствующим образом опубликованным инструктивным письмам по оргполитике, и любые приказы, финансовые директивы и рекомендации должны лишь обеспечивать соблюдение существующей оргполитики.

This is why one “short cycles” an area. By that is meant doing a short start-change-stop that COMPLETES that action.

This is why one (a) instant hats, (b) gets production, (c) does a mini hat P/L on the person, (d) gets production, (e) does another P/L, (f) gets production.

The Produce is a test to the Esto of whether or not he is winning on a post.

You cover your whole area as an Esto with short cycles you can complete on each person individually.

You do group drills of the whole group, little by little.

Gradient scales are at work here. (Look it up if you don’t know it.)

Like, found one basic product for each in the div. Then handled other things. Then got product moved to Exchange on each one. Then did other things. Etc., etc.

The other things are find a Why for a jam area or handle a blow or any other Esto

duty.But don’t spend 82 hours hatting Joe who then doesn’t make it while the rest go hang.

Dev-t drops little by little and production rises IF you short cycle your actions.

Don’t get “stuck in.” “I’ve been working on Dept 1 and it is better now. Next month I go to Dept 2” is a wrong look.

Short cycles. Each staff member getting attention individually as well as a group.

If one man was totally hatted and all the rest not, they’d just knock his hat off anyway.

Don’t get stuck in on a dev-t terminal. Instruct, cram, retread, dismiss is the sequence.

Short cycles work. They show up the good as well as the bad. This gives upstats a reward.

Never have a situation where a Product Officer can say to you, “I appreciate all the trouble you’re taking getting Oscar hatted. Let me know some day when you’ve

finished so I can stop holding the div together and get on with my product.”

Little by little a whole group makes it. Drilled as a group as on org bds. Hatted on one product or a P/L as an individual.

In between you work like mad to get up an org bd and groove in the new staff member or find the WHY the Exec Esto is so anxious to get.

If 2 days pass and a staff member has not had any individual attention, no matter how brief, from an Esto, that Esto has gotten “stuck in.”

Stay unstuck!

Flow. Be mobile.

You can, you know. And be very effective too.